Skip to main content

This is a new service – your feedback will help us to improve it.

Buckinghamshire Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

South Bucks Council (No. 12) Tree Preservation Order 1992; dated 10/11/92; made under Sections 198;

reference
ZZZZZTESRW188
name
South Bucks Council (No. 12) Tree Preservation Order 1992; dated 10/11/92; made under Sections 198;
tree-preservation-order

undefined

TPO/SBDC/1992/12
tree-preservation-zone-type
geometry
MULTIPOLYGON (((-0.494718 51.577833,-0.495338 51.578061,-0.495540 51.578127,-0.496253 51.578319,-0.496627 51.578368,-0.496686 51.578350,-0.496724 51.578321,-0.496748 51.578294,-0.496765 51.578258,-0.496769 51.578206,-0.496762 51.578181,-0.496713 51.578125,-0.496484 51.578055,-0.495432 51.577791,-0.495207 51.577729,-0.495044 51.577670,-0.494845 51.577580,-0.494447 51.577383,-0.494068 51.577163,-0.493846 51.577015,-0.493628 51.576834,-0.493404 51.576620,-0.493199 51.576353,-0.493061 51.576192,-0.492812 51.575823,-0.492645 51.575449,-0.492457 51.574970,-0.492397 51.574788,-0.492347 51.574737,-0.492245 51.574708,-0.492135 51.574710,-0.492051 51.574739,-0.492016 51.574766,-0.492000 51.574783,-0.491996 51.574830,-0.492058 51.575055,-0.492248 51.575560,-0.492355 51.575796,-0.492559 51.576136,-0.492780 51.576438,-0.493045 51.576760,-0.493256 51.576963,-0.493493 51.577144,-0.493716 51.577300,-0.494036 51.577498,-0.494466 51.577735,-0.494718 51.577833)))
point
POINT (-0.493892 51.576817)
notes
organisation
entry-date
2017-07-04
start-date
2017-07-04
end-date

How to fix this issue

Your dataset is missing the tree-preservation-order column.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Buckinghamshire Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL